home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: uucp-1.csn.net!slimer!bgeerdes
- From: bgeerdes@igs.com (Bruce Geerdes)
- Subject: Re: Rogue Wave bug? / How buggy is Rogue Wave?
- Message-ID: <1996Jan5.155910.9618@igs.com>
- Organization: Igs, Inc.
- X-Newsreader: TIN [version 1.2 PL2]
- References: <DKo7KB.6KL@unx.sas.com>
- Date: Fri, 5 Jan 96 15:59:10 GMT
-
- Russell Gonsalves (sasrag@ramanujn.unx.sas.com) wrote:
- > It seems to badly handle null-strings. The last
- > print still prints yy. While test.isNull() is
- > aware that the string is a null-terminated string,
- > such a RWCString cast to const char * does not
- > point to "". This appears to defeat the otherwise
- > seamless and elegant conversion between RWCStrings
- > and character pointers.
-
- It is not a problem with casting RWCString to "const char *". If you change
- the line
-
- test = ""
-
- to
-
- RWCString blank;
- test = blank;
-
- it works; test is empty. It seems that RWCStrings do not like being assigned
- to "". Another way to empty test is:
-
- test.resize(0);
-
- --
- bgeerdes@igs.com (Bruce Geerdes)
-